Control of services at a cell level or a sector level

ABSTRACT

A device may connect to a base station included in a service provider network. The base station may serve a geographic area where the device is located. The device may receive service information associated with the base station. The service information may correspond to the geographic area served by the base station, and may include an access state associated with a service. The access state may indicate a manner in which the device is permitted to access the service via the base station. The device may provide information associated with the access state to cause the device to access the service in accordance with the access state.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.14/445,418, filed Jul. 29, 2014, which is incorporated herein byreference.

BACKGROUND

A base station (e.g., an eNodeB (eNB), a base transceiver station, etc.)may serve one or more geographic areas (e.g., cells, sectors, etc.) inorder to provide cellular coverage to a user device, located within oneof the one or more geographic areas, to allow the user device to accessa service (e.g., a voice service, a data service, etc.) via a connectionwith the base station.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1C are diagrams of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIG. 4 is a flow chart of an example process for receiving, storing, andproviding service information associated with a base station;

FIGS. 5A and 5B are diagrams of an example implementation relating tothe example process shown in FIG. 4;

FIG. 6 is a call flow diagram of an example process for determining anaccess state, associated with a user device connecting to a basestation, based on service information associated with the base station;

FIGS. 7A and 7B are diagrams of an example implementation relating tothe example process shown in FIG. 6;

FIG. 8 is a call flow diagram of an example process for determining anaccess state, associated with a user device being handed over from aserving base station to a target base station, based on serviceinformation associated with the target base station;

FIGS. 9A and 9B are diagrams of an example implementation relating tothe example process shown in FIG. 8; and

FIG. 10 is a flow chart of an example process for determining an accessstate, associated with a user device, based on service informationassociated with a base station.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A user device may be capable of accessing a service (e.g., a voiceservice, a data service, etc.), provided by a service provider network,via a base station that serves a geographic area (e.g., a cell, asector, etc.), in which the user device is located. Presently, theservice provider may be capable of controlling whether the service isavailable in large geographic area, such as a tracking area (e.g.,associated with a mobility management entity (MME)) that includes thebase station and one or more other base stations. However, the serviceprovider may wish to exercise a greater level of control over theservice (e.g., whether a feature of the service is enabled or disabled,whether the service is available, etc.) within a small geographic area(e.g., a particular cell, a particular sector, etc.). Implementationsdescribed herein may allow a service provider to control access to aservice and/or a manner in which the service may be accessed within ageographic area served by a base station and/or within a portion of thegeographic area served by the base station (e.g., a cell, a sector,etc.).

While the processes and/or methods described herein are describedprimarily in the context of a service provider controlling access to aservice within a geographic area associated with a cell, these processesand/or methods may equally apply to a service provider controllingaccess to a service within one or more other geographic areas, such as ageographic area associated with a base station (e.g., including multiplecells), a geographic area associated with a sector (e.g., within acell), or another geographic area.

FIGS. 1A-1C are diagrams of an overview of an example implementation 100described herein. For the purposes of example implementation 100, and asshown in FIG. 1A, assume that base station X, included in a serviceprovider network, is configured such that base station X may allow agroup of user devices, connected to base station X and located withingeographic areas corresponding to three cells (e.g., cell 1, cell 2,cell 3), to access a group of services (e.g., service 1 through serviceN).

As shown in FIG. 1B, assume that the service provider may provideservice information, associated with controlling the group of services,to base station X via a service control device. As shown by referencenumber 105, the service control device may determine (e.g., based onoperator input) service information associated with cell 1, cell 2, andcell 3, and may provide the service information to base station X. Asshown, the service information for each cell may include serviceinformation associated with service 1 through service N, and may includeinformation that identifies an access state (e.g., a manner in which auser device may access a service) for each service within each cell. Asshown, access states may vary across services, and/or cells. Forexample, a user device located in cell 1 may access service 1 inaccordance with access state A, whereas a user device located in cell 2may access service 1 in accordance with access state B. As shown byreference number 110, base station X may store the service information.

For the purposes of FIG. 1C, assume that a user device is located incell 1, and that the user device is establishing a connection (e.g.,after powering on, as a result of a handover decision, etc.) with basestation X. As shown by reference number 115, base station X may provide,to the user device, the cell 1 service information when the user deviceis establishing a connection with base station X. As shown by referencenumber 120, the user device may receive the cell 1 service information,and may determine (e.g., based on the cell 1 service informationassociated with service 1 through service N), a set of service accessstates corresponding to services 1 through N.

As shown by reference number 125, the user device may provideinformation associated with the service 1 access state to a service 1server. Similarly, as shown by reference number 130, the user device mayprovide information associated with the service N access state to aservice N server. In some implementations, the user device may alsostore the information associated with the access states and/or mayupdate service clients (e.g., applications hosted by the user device)that correspond to services associated with each access state. The userdevice and/or the service server (e.g., corresponding to each service)may then permit the user device to access service 1 through service N inaccordance with the access state corresponding to each service.

In this way, a service provider may control access to a service and/or amanner in which the service may be accessed within a geographic areaserved by a base station and/or within a portion of the geographic areaserved by the base station (e.g., a cell, a sector, etc.).

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include a user device 210, one or more basestations 220-1 through 220-M (M≥1) (hereinafter referred to collectivelyas base stations 220, and individually as base station 220), a network230, a service control device 240, and a service server 250. Devices ofenvironment 200 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

User device 210 may include a device capable of receiving, generating,storing, processing, and/or providing information associated with aservice accessible by user device 210 via base station 220. For example,user device 210 may include a communications and/or computing device,such as a mobile phone (e.g., a smart phone, a radiotelephone, etc.), alaptop computer, a tablet computer, a handheld computer, a gamingdevice, or a similar device. In some implementations, user device 210may connect to base station 220 in order to access a service provided,by service server 250, via base station 220 and/or network 230.

Base station 220 may include one or more devices capable of transferringtraffic, associated with a service, destined for and/or received fromuser device 210. In some implementations, base station 220 may includean eNB, a base transceiver station, etc. that receives traffic fromand/or sends traffic to network 230. Base station 220 may send trafficto and/or receive traffic from user device 210 via an air interface. Insome implementations, base station 220 may be configured to allow userdevices 210, connected to base station 220 and located within one ormore geographic areas (e.g., cells, sectors, etc.), to access servicesprovided by service servers 250 via network 230. In someimplementations, base station 220 may include a small cell base station,such as a base station of a microcell, a picocell, and/or a femtocell.In some implementations, base station 220 may act as a serving basestation 220 (e.g., a base station 220 to which user device 210 isconnected in order to access a service). Additionally, or alternatively,base station 220 may act as a target base station 220 (e.g., a basestation 220 to which user device 220 is to be handed over in order toaccess a service).

Network 230 may include one or more wired and/or wireless networks. Forexample, network 230 may include a cellular network (e.g., a long termevolution (LTE) network, a third generation (3G) network, a codedivision multiple access (CDMA) network, etc.), a public land mobilenetwork (PLMN), a local area network (LAN), a wide area network (WAN), ametropolitan area network (MAN), a telephone network (e.g., the PublicSwitched Telephone Network (PSTN)), a private network, an ad hocnetwork, an intranet, the Internet, a fiber optic-based network, a cloudcomputing network, and/or a combination of these or another type ofnetwork.

Service control device 240 may include a device capable of receiving,generating, storing, processing, and/or providing service informationassociated with base station 220. For example, service control device240 may include a server device or a group of server devices. In someimplementations, service control device 240 may be capable ofdetermining (e.g., based on operator input, based on informationreceived from another device, etc.) service information associated withbase station 220. Additionally, or alternatively, service control device240 may be capable of providing service information to base station 220.

Service server 250 may include a device capable of receiving,generating, storing, processing, and/or providing information associatedwith a service that may be accessed by user device 210 (e.g., via basestation 220). For example, service server 250 may include a serverdevice or a group of server devices. In some implementations, serviceserver 250 may be capable of communicating with user device 210 (e.g.,via base station 220, via network 230) in order to provide a service touser device 210. Additionally, or alternatively, service server 250 maybe capable of receiving, determining, processing, and/storinginformation associated with an access state, corresponding to userdevice 210, for the service provided by service server 250.

The number and arrangement of devices and networks shown in FIG. 2 isprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to user device 210, base station 220, service controldevice 240, and/or service server 250. In some implementations, userdevice 210, base station 220, service control device 240, and/or serviceserver 250 may include one or more devices 300 and/or one or morecomponents of device 300. As shown in FIG. 3, device 300 may include abus 310, a processor 320, a memory 330, a storage component 340, aninput component 350, an output component 360, and a communicationinterface 370.

Bus 310 may include a component that permits communication among thecomponents of device 300. Processor 320 may include a processor (e.g., acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), etc.), a microprocessor, and/or anyprocessing component (e.g., a field-programmable gate array (FPGA), anapplication-specific integrated circuit (ASIC), etc.) that interpretsand/or executes instructions. Memory 330 may include a random accessmemory (RAM), a read only memory (ROM), and/or another type of dynamicor static storage device (e.g., a flash memory, a magnetic memory, anoptical memory, etc.) that stores information and/or instructions foruse by processor 320.

Storage component 340 may store information and/or software related tothe operation and use of device 300. For example, storage component 340may include a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, etc.), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of computer-readable medium, along with acorresponding drive.

Input component 350 may include a component that permits device 300 toreceive information, such as via user (e.g., operator) input (e.g., atouch screen display, a keyboard, a keypad, a mouse, a button, a switch,a microphone, etc.). Additionally, or alternatively, input component 350may include a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, an actuator,etc.). Output component 360 may include a component that provides outputinformation from device 300 (e.g., a display, a speaker, one or morelight-emitting diodes (LEDs), etc.).

Communication interface 370 may include a transceiver-like component(e.g., a transceiver, a separate receiver and transmitter, etc.) thatenables device 300 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes in response to processor 320 executingsoftware instructions stored by a computer-readable medium, such asmemory 330 and/or storage component 340. A computer-readable medium isdefined herein as a non-transitory memory device. A memory deviceincludes memory space within a single physical storage device or memoryspace spread across multiple physical storage devices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 is provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for receiving, storing,and providing service information associated with a base station. Insome implementations, one or more process blocks of FIG. 4 may beperformed by base station 220. Additionally, or alternatively, one ormore process blocks of FIG. 4 may be performed by another device or agroup of devices separate from or including base station 220, such asservice control device 240.

As shown in FIG. 4, process 400 may include determining serviceinformation associated with a base station (block 410). For example,base station 220 may determine service information associated with basestation 220. In some implementations, base station 220 may determine theservice information when another device provides the service informationto base station 220. Additionally, or alternatively, base station 220may determine the service information when base station 220 receives anindication to determine the service information.

Service information may include information, associated with basestation 220, that identifies a manner in which one or more services,provided via base station 220, may be accessed by user devices 210connected to base station 220. For example, the service information mayinclude information that identifies a service that may (or may not) beaccessed by user device 210 via base station 220 (e.g., a name of theservice, a service identifier), information that identifies a type ofthe service (e.g., a voice service, a video service, a data service,etc.), information that identifies an access state associated with theservice (e.g., one or more instructions, one or more numericalinstructions, etc.), or another type of information. In someimplementations, the service information may include informationcorresponding to multiple services.

An access state, associated with a service, may indicate a manner inwhich the service may be accessed (e.g., via base station 220) by userdevice 210. In some implementations, the access state may includeinformation indicating whether a service may be accessed by user device210, information indicating whether a feature, aspect, attribute, etc.of the service may be accessed by user device 210, and/or another typeof information. For example, an access state for a voice over internetprotocol (VoIP) service may indicate whether the VoIP service may beaccessed by user device 210 via base station 220. As another example,the access state for the VoIP service may indicate that the VoIP servicemay be accessed by user device 210, and may indicate that user device210 may access the VoIP service to place a VoIP call (e.g., mobileoriginating (MO) calls are enabled), but may also indicate that userdevice 210 may not access the VoIP service to receive a VoIP call (e.g.,mobile terminating (MT) calls are disabled). As yet another example, theaccess state may indicate whether user device 210, while on a VoIP callwhen being handed over to base station 220, may continue the VoIP call.

In some implementations, the access state may be represented by one ormore instructions (e.g., MO Enabled=YES, MT Enabled=NO, etc.).Additionally, or alternatively, the access state may be represented by astring of characters (e.g., 1, 001, 2C3B, 4#A&, etc.) to be interpretedby user device 210. For example, when the access state includes acharacter string, base station 220 may determine (e.g., based oninformation received from service control device 240) mappinginformation associated with interpreting the character string thatrepresents the access state, and may broadcast (e.g., periodically, whenthe mapping information is updated, etc.) the mapping information touser devices 210 (e.g., and user devices 210 may store the mappinginformation). Additionally, or alternatively, user device 210 mayreceive (e.g., via network 230) the mapping information from anotherdevice, associated with the network operator. For example, user device210 may receive the mapping information during a subscriber identitymodule (SIM) provisioning procedure associated with user device 210. Inthis way, user device 210 may be capable of interpreting the accessstate represented by the character string based on the mappinginformation (e.g., when user device 210 receives the serviceinformation, as described below). In some implementations, a set ofcharacter strings (e.g., that corresponds to a set of access states) maybe standardized such that multiple user devices 210 and/or multiple basestations 220 may use the set of character strings.

In some implementations, the service information may be associated withbase station 220. For example, the service information may includeservice information associated with controlling access to serviceswithin a geographic area served by base station 220 (e.g., all cellsand/or sectors served by base station 220). Additionally, oralternatively, the service information may be associated withcontrolling access to services within one or more cells served by basestation 220. For example, the service information may include serviceinformation associated with controlling access to services within ageographic area corresponding to a particular cell served by basestation 220. Additionally, or alternatively, the service information maybe associated with controlling access to services within one or moresectors served by base station 220.

In some implementations, base station 220 may determine the serviceinformation based on information provided by service control device 240.For example, service control device 240 may receive operator input(e.g., from a user associated with the service provider) that identifiesservice information for one or more services associated with basestation 220, and may provide the service information to base station220. In this example, base station 220 may receive the serviceinformation from service control device 240.

Additionally, or alternatively, base station 220 may determine theservice information based on information stored by base station 220. Forexample, base station 220 may store a service information algorithm,associated with a service, that causes base station 220 to update (e.g.,automatically, dynamically, etc.) service information, associated withthe service, based on one or more performance metrics (e.g., a qualityof service level, a cell capacity consumption, a service blockingstatistic, etc.), associated with the service, that may be observed,measured, determined, etc. by base station 220. In this example, basestation 220 may provide information associated with the one or moreperformance metrics as input to the service information algorithm, andmay receive, as output, the service information and/or information thatidentifies a manner in which base station 220 is to update, alter,and/or modify existing service information.

As further shown in FIG. 4, process 400 may include storing the serviceinformation associated with the base station (block 420). For example,base station 220 may store the service information associated with basestation 220. In some implementations, base station 220 may store theservice information when base station 220 determines the serviceinformation (e.g., after base station 220 determines the serviceinformation). Additionally, or alternatively, base station 220 may storethe service information based on receiving information, indicating thatbase station 220 is to store the service information, from anotherdevice, such as service control device 240.

In some implementations, base station 220 may store the serviceinformation in a memory location (e.g., a RAM, a ROM, a cache, a harddisk, etc.) of base station 220. Additionally, or alternatively, basestation 220 may provide the service information to another device forstorage.

In some implementations, base station 220 may store informationassociated with the service information such that previous serviceinformation (e.g., service information determined by base station 220 atan earlier time) is overwritten and/or deleted. Additionally, oralternatively, base station 220 may store the service information suchthat base station 220 may retrieve the service information at a latertime.

As further shown in FIG. 4, process 400 may include providing theservice information associated with the base station (block 430). Forexample, base station 220 may provide the service information associatedwith the base station. In some implementations, base station 220 mayprovide the service information after base station 220 determines and/orstores the service information. Additionally, or alternatively, basestation 220 may provide the service information when user device 210connects to base station 220. Additionally, or alternatively, basestation 220 may provide the service information when base station 220receives, from another device, an indication that base station 220 is toprovide the service information.

In some implementations, base station 220 may provide the serviceinformation to user devices 210 connected to base station 220 when basestation 220 determines the service information. For example, a group ofuser devices 210 (e.g., located in a particular cell served by basestation 220) may be connected to base station 220 when base station 220determines the service information. In this example, if the serviceinformation includes updated service information associated with theparticular cell, then base station 220 may notify (e.g., by raising abroadcast update flag) the group of user devices 210 that base station220 has determined updated service information. Here, the group of userdevices 210 may read (e.g., based on the broadcast update flag) abroadcast message, provided by base station 220, that includes theupdate service information. In this way, base station 220 may provide(e.g., broadcast) the update service information to the group of userdevices 210 in order to allow the group of user devices 210 to receivethe update service information. Each user device 210, of the group ofuser devices 210, may receive the updated service information associatedwith the particular cell, and may act upon the service information asnecessary, as described below.

Additionally, or alternatively, base station 220 may provide the serviceinformation to user device 210 when user device 210 connects to basestation 220 (e.g., an initial connection to base station 220, a handoverto base station 220, etc.), as described below.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIGS. 5A and 5B are diagrams of an example implementation 500 relatingto example process 400 shown in FIG. 4. For the purposes of exampleimplementation 500, and as shown in FIG. 5A, assume that a base station220 (e.g., eNB-A), included in a service provider network, is configuredsuch that eNB-A may allow user devices 210, connected to eNB-Z andlocated within geographic areas corresponding to three cells (e.g., cell1, cell 2, cell 3), to access a VoIP service provided by a VoIP server.

As shown in FIG. 5B, assume that the service provider provides serviceinformation, associated with controlling access to the VoIP service, toeNB-A via service control device 240 (e.g., SCD1). As shown by referencenumber 510, SCD1 may determine (e.g., based on operator input) cell 1service information for user devices 210 located in cell 1 that accessthe VoIP service through eNB-A. As shown, the cell 1 service informationmay indicate that user device 210 (e.g., located in cell 1 and accessingthe VoIP service through eNB-A) may not place a VoIP call (e.g., MOCalls=NO), may indicate that user device 210 may receive a VoIP call(e.g., MT calls=YES), and may indicate that user device 210 may stay ona VoIP call that is in progress when user device 210 located within cell1 is handed over to eNB-A. As further shown, SCD1 may determine (e.g.,based on information stored by SCD1) an access state (e.g., VoIP AccessState=5) that represents the cell 1 service information. As shown byreference number 520, SCD1 may provide the cell 1 service information,associated with eNB-A, to eNB-A. While example implementation 500 isdescribed in the context of service information associated with a singleservice (e.g., the VoIP service), in other example implementations, SCD1may determine and provide service information, associated with access tomultiple services (e.g., in addition to the VoIP service) via cell 1, toeNB-A.

As shown by reference number 530, eNB-A may receive the cell 1 serviceinformation, and may store the cell 1 service information. As shown byreference number 540, eNB-A may raise a broadcast flag, associated withcell 1, and may include the cell 1 service information within a cell 1message broadcasted to user devices 210 (e.g., UD1 and UD2) located incell 1 and connected to eNB-A. As shown by reference number 550, UD1 andUD2 may determine (e.g., based on the broadcast flag raised by eNB-A)that UD1 and UD2 are to read the cell 1 broadcast message, and may readthe cell 1 broadcast message and receive the cell 1 service information.UD1 and UD2 may then act upon the cell 1 service information asnecessary, as described below.

As indicated above, FIGS. 5A and 5B are provided merely as an example.Other examples are possible and may differ from what was described withregard to FIGS. 5A and 5B.

FIG. 6 is a call flow diagram of an example process 600 for determiningan access state, associated with a user device connecting to a basestation, based on service information associated with the base station.In some implementations, one or more operations of FIG. 6 may beperformed by one or more devices included in environment 200.

As shown in FIG. 6, process 600 may include sending a connection requestassociated with a user device and a base station (shown at referencenumber 605). For example, user device 210 may send a connection requestassociated with user device 210 and base station 220. In someimplementations, user device 210 may send the connection request whenuser device 210 is not connected to any base station 220.

A connection request may include a request associated with requesting aconnection between user device 210 and base station 220 such that userdevice 210 may access a service, provided by service server 250, viabase station 220 and/or network 230. For example, user device 210, whennot connected to any base station 220 (e.g., when user device 210powers-on, when user device 210 wakes up from an idle mode, etc.), mayinitiate communication with base station 220, serving a geographic areawhere user device 210 is located, by sending a random-access (RA)preamble to base station 220, and may receive an RA response from basestation 220. In this example, user device 210 may then send a radioresource control (RRC) connection request to base station 220.Additionally, or alternatively, user device 210 may send another type ofconnection request associated with requesting a connection between userdevice 210 and base station 220.

As further shown in FIG. 6, process 600 may include determining serviceinformation associated with the base station (shown at reference number610). For example, base station 220 may determine service informationassociated with base station 220. In some implementations, base station220 may determine the service information after user device 210 sendsthe connection request (e.g., after base station 220 receives theconnection request). Additionally, or alternatively, base station 220may determine the service information when base station 220 is preparingto send, to user device 210, connection information associated withestablishing a connection between user device 210 and base station 220.

In some implementations, base station 220 may determine the serviceinformation based on information stored by base station 220. Forexample, base station 220 may receive and store service informationassociated with base station 220 (e.g., as described above), and basestation 220 may determine the service information based on the storedservice information. Additionally, or alternatively, base station 220may determine the service information based on information received fromservice control device 240. For example, base station 220 may receivethe connection request from user device 210, and may send a serviceinformation request to service control device 240. In this example, basestation 220 may determine the service information based on a responseprovided by service control device 240.

In some implementations, base station 220 may determine serviceinformation associated with a geographic area where user device 210 islocated. For example, if user device 210 is located in a particular cellserved by base station 220, then base station 220 may determine serviceinformation that corresponds to the particular cell served by basestation 220 (e.g., when the service information differs across cellsserved by base station 220). As another example, if user device 210 islocated in a particular cell served by base station 220, then basestation 220 may determine service information that corresponds to basestation 220 (e.g., when the service information, stored by base station220, is to be applied to all cells served by base station 220). As yetanother example, if user device 210 is located in a particular sector(e.g., within a cell served by base station 220), then base station 220may determine service information that corresponds to the particularsector served by base station 220 (e.g., when the service informationdiffers across sectors within a cell served by base station 220).

As further shown in FIG. 6, process 600 may include providing connectioninformation, including the service information associated with the basestation, to the user device (shown at reference number 615). Forexample, base station 220 may provide connection information, includingthe service information associated with base station 220, to user device210. In some implementations, base station 220 may provide theconnection information to user device 210 after base station 220determines the service information.

Connection information may include information associated withestablishing a connection between user device 210 and base station 220such that user device 210 may access a service provided by serviceserver 250 via base station 220 and/or network 230. For example, basestation 220 may send (e.g., in response to an RRC connection request)RRC connection setup information and/or RRC connection reconfigurationinformation that allows the connection between user device 210 and basestation 220 to be established. In this example, base station 220 mayinclude the service information, associated with base station 220,within the RRC connection setup information and/or within the RRCconnection reconfiguration information provided to user device 210.Additionally, or alternatively, as described above, user device 210 mayreceive the service information, associated with base station 220, at anearlier timer via a broadcast message. Additionally, or alternatively,base station 220 may send another type of connection informationassociated with establishing a connection between user device 210 andbase station 220. In some implementations, user device 210 may receivethe connection information, and may establish the connection betweenuser device 210 and base station 220 based on the connectioninformation.

As further shown in FIG. 6, process 600 may include determining anaccess state, associated with the user device and the service, based onthe service information associated with the base station (shown atreference number 620). For example, user device 210 may determine anaccess state, associated with user device 210 and the service providedby service server 250, based on the service information associated withbase station 220. In some implementations, user device 210 may determinethe access state after user device 210 receives the service informationfrom base station 220. Additionally, or alternatively, user device 210may determine the access state when user device 210 establishes theconnection between user device 210 and base station 220.

As discussed above, an access state, associated with a service, mayinclude information indicating a manner in which the service may beaccessed (e.g., via base station 220) by user device 210. In someimplementations, user device 210 may determine the access state based onthe service information (e.g., when the service information includesinformation associated with the access state). In some implementations,user device 210 may determine multiple access states that correspond tomultiple services identified in the service information.

In some implementations, user device 210 may determine the access stateby interpreting the access state included in the service information.For example, if the access state, associated with the service, isrepresented by a string of characters, then user device 210 mayinterpret (e.g., based on mapping information stored by user device 210)the access state, as described above. In this example, user device 210may interpret the access state by identifying whether one or morefeatures, aspects, attributes, etc. of the service may be accessed byuser device 210.

As further shown in FIG. 6, process 600 may include providinginformation associated with the access state (shown at reference number625). For example, user device 210 may provide information associatedwith the access state. In some implementations, user device 210 mayprovide the information associated with access state after user device210 determines the access state. Additionally, or alternatively, userdevice 210 may provide the information associated with access stateafter user device 210 receives an indication to provide the informationassociated with the access state.

In some implementations, user device 210 may provide the informationassociated with the access state to cause user device 210 to access theservice, associated with the access state, in accordance with the accessstate. For example, if user device 210 determines information indicatingthat user device 210 may access a particular feature of the service,then user device 210 may provide the information associated with theaccess state in order to enable user device 210 to access the feature ofthe service. As another example, if user device 210 determinesinformation indicating that user device 210 may not access the service,then user device 210 may provide the information associated with theaccess state in order to disable user device 210 from accessing theservice.

In some implementations, user device 210 may provide the informationassociated with the access state to a service client, hosted by userdevice 210, associated with the service. For example, if the accessstate indicates that MO calls, associated with a VoIP service, are to bedisabled, then user device 210 may provide, to a VoIP client hosted byuser device 210, information that causes the VoIP client to disable MOcalls.

Additionally, or alternatively, user device 210 may provide theinformation associated with the access state to service server 250associated with the service. For example, if the access state indicatesthat MT calls, associated with a VoIP service, are to be disabled, thenuser device 210 may provide, to service server 250 associated with theVoIP service, information that causes service server 250 to prevent userdevice 210 from receiving MT calls provided via service server 250. Inthis example, service server 250 may receive the information associatedwith the access state, and may determine another manner in which tohandle MT VoIP calls destined for user device 210 (e.g., service server250 may determine that a MT VoIP call to user device 210 is to be routedvia a CDMA network, is to be routed to voicemail, is to be presentedwith a message the that MT VoIP call cannot be completed, etc.).

In some implementations, user device 210 may provide informationassociated with a first access state for a first service to a firstservice client and/or a first service server 250, information associatedwith a second access state for a second service to a second serviceclient and/or a second service server 250 (e.g., such that user device210 provides information associated with multiple access statescorresponding to multiple services identified in the serviceinformation).

Although FIG. 6 shows example operations of process 600, in someimplementations, process 600 may include additional operations, feweroperations, different operations, or differently arranged operationsthan those depicted in FIG. 6. Additionally, or alternatively, two ormore of the operations of process 600 may be performed in parallel.

FIGS. 7A and 7B are diagrams of an example implementation 700 relatingto example process 600 shown in FIG. 6. For the purposes of exampleimplementation 700, assume that base station 220, identified as eNB-A,stores service information associated with a group of cells (e.g.,including cell 1) served by eNB-A. Further, assume that user device 210(e.g., identified as UD3) is located in a geographic area correspondingto cell 1 and is not connected to any base station 220 (e.g., when UD3is in a dormant state or is powered off).

As shown in FIG. 7A, and by reference number 705, UD3 may betransitioning to an activate state (e.g., from a dormant state) orpowering on and, as shown by reference number 710, may send, to eNB-A,an RRC connection request associated with establishing a connectionbetween UD3 and eNB-A. As shown by reference number 715, eNB-A mayreceive the RRC connection request, and may determine cell 1 serviceinformation associated with eNB-A (e.g., since UD3 is located in cell1). As shown, the cell 1 service information may include informationidentifying an access state for a VoIP service (e.g., VoIP AccessState=5) to be accessed by user devices 210 when located in cell 1 andconnected to eNB-A. As shown by reference number 720, eNB-A may provide(e.g., as part of a process for establishing a connection between UD3and eNB-A) RRC connection reconfiguration information to UD3. As shown,the RRC connection reconfiguration information may include the cell 1service information. As shown by reference number 725, UD3 may establishthe connection between UD3 and eNB-A based on receiving the RRCconnection reconfiguration information (e.g., including the cell 1service information).

As shown in FIG. 7B, and by reference 730, UD3 may receive the serviceinformation, may identify the access state for the VoIP service (e.g.,VoIP Access State=5), and may interpret (e.g., based on informationstored by UD3) the access state to determine information associated withthe UD3 VoIP access state (e.g., UD3 VoIP Access State: MO=Yes, MT=No,Handover=Yes). As shown by reference number 735, UD3 may provide theinformation associated with UD3 VoIP access state to a VoIP client,hosted by UD3, that causes UD3 to enable a MO call feature of the VoIPservice (e.g., such that UD3 may place a VoIP call). As shown byreference number 740, UD3 may also provide the information associatedwith the UD3 VoIP access state to a VoIP server (e.g., associated withproviding the VoIP service). As shown by reference number 745, the VoIPserver may receive the information associated with the UD3 VoIP accessstate and may update information, stored by the VoIP server, such thatthe VoIP service may be accessed by UD3 in accordance with theinformation associated with the UD3 VoIP access state (e.g., the VoIPserver update the information such that UD3 may not receive MT VoIPcalls via the VoIP service).

As indicated above, FIGS. 7A and 7B are provided merely as an example.Other examples are possible and may differ from what was described withregard to FIGS. 7A and 7B.

FIG. 8 is a call flow diagram of an example process 800 for determiningan access state, associated with a user device being handed over from aserving base station to a target base station, based on serviceinformation associated with the target base station. In someimplementations, one or more operations of FIG. 8 may be performed byone or more devices included in environment 200.

While the process of FIG. 8 is described in the context of user device210 being handed over from serving base station 220 to target basestation 220, this process equally apply to user device 210 being handedover in another manner, such as a from a serving cell to a target cell,a serving sector to a target sector, a serving base station (eNB) to atarget base station (eNB), etc.

As shown in FIG. 8, process 800 may include providing a measurementreport associated with a user device and a serving base station (shownat reference number 805). For example, user device 210 may provide ameasurement report associated with user device 210 and serving basestation 220. In some implementations, user device 210 may provide themeasurement report when user device 210 determines the measurementreport. Additionally, or alternatively, user device 210 may provide themeasurement report when user device 210 receives an indication that userdevice 210 is to send the measurement report.

A measurement report may include information associated with determiningwhether user device 210 is to be handed over from serving base station220 to target base station 220. For example, user device 210 may measureinformation (e.g., signal strength information, signal qualityinformation, etc.) associated with serving base station 220, target basestation 220, a serving cell, a target cell, etc. and may provide (e.g.,periodically, based on a threshold condition being satisfied, etc.) theinformation, in the form of a measurement report, to serving basestation 220.

As further shown in FIG. 8, process 800 may include determining that theuser device is to be handed over from the serving base station to atarget base station (shown at reference number 810). For example,serving base station 220 may determine that user device 210 is to behanded over from serving base station 220 to target base station 220. Insome implementations, serving base station 220 may determine that userdevice 210 is to be handed over to target base station 220 after userdevice 210 provides the measurement report. Additionally, oralternatively, serving base station 220 may determine that user device210 is to be handed over to target base station 220 when serving basestation 220 receives an indication that serving base station 220 is todetermine whether user device 210 is to be handed over to target basestation 220. For example, serving base station 220 may receive, fromtarget base station 220, an indication that user device 210 is to behanded over to target base station 220.

In some implementations, serving base station 220 may determine thatuser device 210 is to be handed over to target base station 220 based onthe measurement report. For example, serving base station 220 may storea handover algorithm associated with determining whether user device 210is to be handed over to target base station 220. In this example,serving base station 220 may provide information associated with themeasurement report as input to the handover algorithm, and may receive,as output, information indicating that user device 210 is to be handedover to target base station 220.

As further shown in FIG. 8, process 800 may include determining serviceinformation associated with the target base station (shown at referencenumber 815). For example, serving base station 220 may determine serviceinformation associated with target base station 220. In someimplementations, serving base station 220 may determine the serviceinformation, associated with target base station 220, after serving basestation 220 determines that user device 210 is to be handed over totarget base station 220. Additionally, or alternatively, serving basestation 220 may determine the service information, associated withtarget base station 220, when serving base station 220 receives theservice information from target base station 220, as described below.

In some implementations, serving base station 220 may determine theservice information, associated with target base station 220, based oninformation stored by target base station 220. For example, serving basestation 220 may communicate with target base station 220 regardinghanding user device 210 to target base station 220, and serving basestation 220 may determine the service information, associated withtarget base station 220, during said communication. As another example,serving base station 220 may request the service information, associatedwith target base station 220, and may determine the service informationbased on a response, provided by target base station 220, that includesthe service information associated with target base station 220.

As further shown in FIG. 8, process 800 may include providing handoverinformation, including the service information associated with thetarget base station, to the user device (shown at reference number 820).For example, serving base station 220 may provide handover information,including the service information associated with target base station220, to user device 210. In some implementations, serving base station220 may provide the handover information to user device 210 afterserving base station 220 determines the service information associatedwith target base station 220. Additionally, or alternatively, servingbase station 220 may provide the service information, associated withtarget base station 220, after serving base station 220 communicateswith target base station 220 regarding handing user device 210 over totarget base station 220.

Handover information may include information associated with handinguser device 210 over, from serving base station 220 to target basestation 220, such that user device 210 may access a service, provided byservice server 250, via target base station 220 and/or network 230. Forexample, serving base station 220 may send, to user device 210, RRCconnection reconfiguration information associated with handing userdevice 210 over from serving base station 220 to target base station220. In this example, serving base station 220 may include the serviceinformation, associated with target base station 220, within the RRCconnection reconfiguration information provided to user device 210.Additionally, or alternatively, serving base station 220 may sendanother type of handover information associated with handing user device210 over from serving base station 220 to target base station 220. Insome implementations, user device 210 may receive the handoverinformation, and may establish a connection between user device 210 andtarget base station 220 based on the handover information.

As further shown in FIG. 8, process 800 may include determining anaccess state, associated with the user device and the service, based onthe service information associated with the target base station (shownat reference number 825). For example, user device 210 may determine anaccess state, associated with user device 210 and the service providedby service server 250, based on the service information associated withtarget base station 220. In some implementations, user device 210 maydetermine the access state after user device 210 receives the serviceinformation, associated with target base station 220, from serving basestation 220. Additionally, or alternatively, user device 210 maydetermine the access state after user device 210 establishes theconnection between user device 210 and target base station 220. Inimplementations, user device 210 may determine and/or interpret theaccess state based on the service information in the manner describedabove.

As further shown in FIG. 8, process 800 may include providinginformation associated with the access state (shown at reference number830). For example, user device 210 may provide information associatedwith the access state. In some implementations, user device 210 mayprovide the information associated with access state after user device210 determines the access state. Additionally, or alternatively, userdevice 210 may provide the information associated with the access stateafter user device 210 receives an indication to provide the informationassociated with the access state. In some implementations, user device210 may provide the information associated with the access state in themanner described above.

In some implementations, if user device 210 is accessing the servicewhen the handover occurs, user device 210 may provide the informationassociated with the access state when user device 210 stops accessingthe service. For example, assume that the information associated withthe access state for a VoIP service indicates that MT calls, associatedwith a VoIP service, are disabled, but also indicates that MT callsinitiated before a handover (e.g., and still ongoing during thehandover) may continue. In this example, user device 210 may wait untilthe ongoing MT VoIP call is terminated, and may then provide (e.g., to aVoIP server) information indicating that MT calls, associated with theVoIP service, are to be disabled (e.g., and the VoIP server may disableMT calls for user device 210 accordingly).

Although FIG. 8 shows example operations of process 800, in someimplementations, process 800 may include additional operations, feweroperations, different operations, or differently arranged operationsthan those depicted in FIG. 8. Additionally, or alternatively, two ormore of the operations of process 800 may be performed in parallel.

FIGS. 9A and 9B are diagrams of an example implementation 900 relatingto example process 800 shown in FIG. 8. For the purposes of exampleimplementation 900, assume that user device 210 (e.g., UD3) is locatedwithin a geographic area corresponding to a first cell (e.g., cell 1)served by a serving base station 220 (e.g., eNB-A), and that UD3 isconnected to eNB-A. Further, assume that target base station 220 (e.g.,eNB-B) serves a geographic area corresponding to a second cell (e.g.,cell 4), and that eNB-B stores service information associated with agroup of cells (e.g., including cell 4) served by eNB-B. Finally, assumethat UD3 is moving from the geographic area corresponding to cell 1 tothe geographic area corresponding to cell 4.

As shown in FIG. 9A, and by reference number 905, UD3 may provide ameasurement report, associated with UD3 and identifying eNB-B, to eNB-A.As shown by reference number 910, eNB-A may receive the measurementreport, and may determine (e.g., based on a handover algorithm stored byeNB-A) that UD3 is to be handed over to eNB-B (e.g., since UD3 is movingfrom cell 1 to cell 4). As shown by reference number 915, eNB-A maycommunicate with eNB-B regarding handing over UD3 from eNB-A to eNB-B,and, as shown, may determine service information for cell 4 thatincludes an access state for user devices 210, located in cell 4 andconnected to eNB-B, accessing a VoIP service (e.g., VoIP AccessState=8). As shown by reference number 920, eNB-A may provide (e.g., aspart of a handover process associated with handing over UD3 to eNB-B)RRC connection reconfiguration information to UD3. As shown, the RRCconnection reconfiguration information may include the cell 4 serviceinformation. As shown by reference number 925, UD3 may establish theconnection between UD3 and eNB-B based on receiving the RRC connectionreconfiguration information (e.g., including the cell 4 serviceinformation).

As shown in FIG. 9B, and by reference 930, UD3 may receive the cell 4service information, may identify the access state for the VoIP service(e.g., VoIP Access State=8), and may interpret (e.g., based oninformation stored by UD3) the access state to determine informationassociated with the UD3 VoIP access state (e.g., UD3 VoIP Access State:MO=No, MT=Yes, Handover=Yes). As shown by reference number 935, UD3 mayprovide the information associated with UD3 VoIP access state to a VoIPclient, hosted by UD3, that causes UD3 to disable a MO call feature ofthe VoIP service (e.g., such that UD3 may not place a VoIP call). Asshown by reference number 940, UD3 may also provide the informationassociated with the UD3 VoIP access state to a VoIP server (e.g.,associated with providing the VoIP service). As shown by referencenumber 945, the VoIP server may receive the information associated withthe UD3 VoIP access state and may update information, stored by the VoIPserver, such that the VoIP service may be accessed by UD3 in accordancewith the information associated with the UD3 VoIP access state (e.g.,the VoIP server update the information such that UD3 may receive MT VoIPcalls via the VoIP service).

As indicated above, FIGS. 9A and 9B are provided merely as an example.Other examples are possible and may differ from what was described withregard to FIGS. 9A and 9B.

FIG. 10 is a flow chart of an example process 1000 for determining anaccess state, associated with a user device, based on serviceinformation associated with a base station. In some implementations, oneor more process blocks of FIG. 10 may be performed by user device 210.Additionally, or alternatively, one or more process blocks of FIG. 10may be performed by another device or a group of devices separate fromor including user device 210, such as base station 220 and/or serviceserver 250.

As shown in FIG. 10, process 1000 may include receiving serviceinformation associated with a base station (block 1010). For example,user device 210 may receive service information associated with basestation 220, as described above.

As further shown in FIG. 10, process 1000 may include determining anaccess state, associated with the user device, based on the serviceinformation (block 1020). For example, user device 210 may determine anaccess state, associated with user device 210 and based on the serviceinformation, as described above.

As further shown in FIG. 10, process 1000 may include providinginformation associated with the access state (block 1030). For example,user device 210 may provide information associated with the accessstate, as described above.

Although FIG. 10 shows example blocks of process 1000, in someimplementations, process 1000 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 10. Additionally, or alternatively, two or more of theblocks of process 1000 may be performed in parallel.

Implementations described herein may permit a service provider tocontrol access to a service and/or a manner in which the service may beaccessed within a geographic area served by a base station and/or withina portion of the geographic area served by the base station (e.g., acell, a sector, etc.).

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, etc.

To the extent the aforementioned embodiments collect, store or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Storage and use ofpersonal information may be in an appropriately secure manner reflectiveof the type of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items,and may be used interchangeably with “one or more.” Where only one itemis intended, the term “one” or similar language is used. Also, as usedherein, the terms “has,” “have,” “having,” or the like are intended tobe open-ended terms. Further, the phrase “based on” is intended to mean“based, at least in part, on” unless explicitly stated otherwise.

What is claimed is:
 1. A base station, comprising: one or more memories;and one or more processors, communicatively coupled to the one or morememories, to: determine one or more performance metrics associated withthe base station; determine, based on the one or more performancemetrics, service information associated with the base station, theservice information corresponding to a portion of a geographic areaserviced by the base station that is less than an entire geographic areaserviced by the base station, and the service information includinginformation that identifies a first access state associated with aservice, the first access state indicating whether a user device,located in the portion of the geographic area serviced by the basestation, is permitted to access the service or access a feature of theservice, the first access state being different from a second accessstate associated with the service, the second access state correspondingto a different portion of the geographic area, serviced by the basestation, that is less than the entire geographic area serviced by thebase station; and provide the service information to the user device tocause the user device to access the service or the feature of theservice based on the first access state.
 2. The base station of claim 1,where the one or more performance metrics include at least one of: aquality of service level associated with the base station; a cellcapacity consumption associated with the base station; or a serviceblocking statistic associated with the base station.
 3. The base stationof claim 1, where the service information is updated service informationassociated with updating, altering, or modifying existing serviceinformation associated with the base station, the existing serviceinformation corresponding to the portion of the geographic area servicedby the base station, and the existing service information beingassociated with the second access state associated with the service. 4.The base station of claim 1, where the one or more processors, whenproviding the service information, are to: broadcast a message to aplurality of user devices connected to the base station, the pluralityof user devices including the user device, and the message including theservice information.
 5. The base station of claim 4, where the one ormore processors are further to: raise a broadcast flag based onreceiving the service information, the broadcast flag being raised tonotify the plurality of user devices to read the message; and where theone or more processors, when broadcasting the message, are to: broadcastthe message based on raising the broadcast flag.
 6. The base station ofclaim 1, where the one or more processors, are further to: establish aconnection with another user device; determine that the other userdevice is located in the portion of the geographic area serviced by thebase station; and provide the service information to the other userdevice based on determining that the other user device is located in theportion of the geographic area.
 7. The base station of claim 1, wherethe portion of the geographic area serviced by the base station is aparticular cell serviced by the base station or a particular sectorserviced by the base station.
 8. A non-transitory computer-readablemedium storing instructions, the instructions comprising: one or moreinstructions that, when executed by one or more processors, cause theone or more processors to: obtain a set of performance metricsassociated with a base station; determine, based on the set ofperformance metrics, service information associated with the basestation, the service information corresponding to a portion of ageographic area, serviced by the base station, that is less than anentire geographic area serviced by the base station, and the serviceinformation including information that identifies a first access stateassociated with a service, the first access state indicating whether auser device, while located in the portion of the geographic areaserviced by the base station, is permitted to access the service oraccess a feature of the service, the first access state being differentfrom a second access state associated with the service, the secondaccess state corresponding to a different portion of the geographicarea, serviced by the base station, that is less than the entiregeographic area serviced by the base station; and provide the serviceinformation to the user device to cause the user device to access theservice or the feature of the service based on the first access state.9. The non-transitory computer-readable medium of claim 8, where the setof performance metrics includes information associated with at least oneof: a quality of service level provided by the base station; a cellcapacity consumption of the base station; or a service blockingstatistic associated with the base station.
 10. The non-transitorycomputer-readable medium of claim 8, where the service information isupdated service information associated with updating, altering, ormodifying existing service information associated with the base station,the existing service information corresponding to the portion of thegeographic area serviced by the base station, and the existing serviceinformation being associated with the second access state associatedwith the service.
 11. The non-transitory computer-readable medium ofclaim 8, where the one or more instructions, that cause the one or moreprocessors to provide the service information, cause the one or moreprocessors to: broadcast a message to a plurality of user devices,connected to the base station, that are located in the portion of thegeographic area serviced by the base station, the plurality of userdevices including the user device, and the message including the serviceinformation.
 12. The non-transitory computer-readable medium of claim11, where the one or more instructions, when executed by the one or moreprocessors, further cause the one or more processors to: raise abroadcast flag based on determining the service information, thebroadcast flag being raised to notify the plurality of user devices toread the message; and where the one or more instructions, that cause theone or more processors to broadcast the message, cause the one or moreprocessors to: broadcast the message based on raising the broadcastflag.
 13. The non-transitory computer-readable medium of claim 8, wherethe one or more instructions, when executed by the one or moreprocessors, further cause the one or more processors to: establish aconnection with another user device; determine that the other userdevice is located in the portion of the geographic area serviced by thebase station; and provide the service information to the other userdevice based on determining that the other user device is located in theportion of the geographic area.
 14. The non-transitory computer-readablemedium of claim 8, where the portion of the geographic area serviced bythe base station is a particular cell serviced by the base station or aparticular sector serviced by the base station.
 15. A method,comprising: determining, by a base station, one or more performancemetrics associated with the base station; determining, based on the oneor more performance metrics, service information associated with thebase station, the service information corresponding to a portion of ageographic area, serviced by the base station, that is less than anentire geographic area serviced by the base station, and the serviceinformation including information that identifies a first access stateassociated with a service, the first access state indicating whether auser device, located in the portion of the geographic area serviced bythe base station, is permitted to access the service or access a featureof the service, the first access state being different from a secondaccess state associated with the service, the second access statecorresponding to a different portion of the geographic area, serviced bythe base station, that is less than the entire geographic area servicedby the base station; and providing, by the base station, the serviceinformation to the user device to cause the user device to access theservice or the feature of the service based on the first access state.16. The method of claim 15, where the one or more performance metricsinclude at least one of: a quality of service level associated with thebase station; a cell capacity consumption associated with the basestation; or a service blocking statistic associated with the basestation.
 17. The method of claim 15, where providing the serviceinformation comprises: broadcasting a message to a plurality of userdevices connected to the base station, the plurality of user devicesincluding the user device, and the message including the serviceinformation.
 18. The method of claim 17, further comprising: raising abroadcast flag based on receiving the service information, the broadcastflag being raised to notify the plurality of user devices to read themessage.
 19. The method of claim 15, further comprising: establishing aconnection with another user device; determining that the other userdevice is located in the portion of the geographic area serviced by thebase station; and providing the service information to the other userdevice based on determining that the other user device is located in theportion of the geographic area.
 20. The method of claim 15, where theportion of the geographic area serviced by the base station is aparticular cell serviced by the base station or a particular sectorserviced by the base station.